System and Method for Processing Expiration Dates for Prepaid Cards

ABSTRACT

A prepaid card processing system is operable for processing customized expiration dates of prepaid cards. The prepaid card processing system includes a database for storing program expiration parameters associated with an issuer prepaid card program; a set of card accounts created under the issuer prepaid card program, wherein each card account has an expiration date for a prepaid card associated with the card account; and one or more customized expiration parameters for the set of card accounts. The prepaid card processing system is operable to determine the expiration date for the prepaid card associated with the card account based on the program expiration parameters and the customized expiration parameters for the set of card accounts.

CROSS-REFERENCE TO RELATED PATENTS

The present U.S. Utility Patent Application claims priority pursuant to35 U.S.C. §119(e) to U.S. Provisional Application Ser. No. 61/083,311entitled “System and Method for Processing Expiration Dates for PrepaidCards,” (Attorney Docket No. P-14185PRV), filed Jul. 24, 2008, pending,which is hereby incorporated herein by reference in its entirety andmade part of the present U.S. Utility Patent Application for allpurposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

Not applicable.

BACKGROUND OF THE INVENTION

1. Technical Field of the Invention

This invention relates generally to systems and methods for processingof prepaid cards and more particularly to processing expiration datesfor prepaid cards.

2. Description of Related Art

Many consumers lack access to a credit card or are without a bankingaccount. Prepaid cards are one solution for such consumers. Prepaidcards are funded with a specific monetary value at issuance and can beused similarly to credit cards to purchase goods and services and toaccess cash with the funded monetary value.

Different types of prepaid cards are currently offered in themarketplace. For example, one type of prepaid card is a “stored valueprepaid card”. A stored value prepaid card is issued by an issuer to acardholder and is enrolled under the cardholder's name. The stored valueprepaid card is prefunded by the cardholder with a specific monetaryvalue. The stored value prepaid card may be reloadable with additionalfunds by the cardholder that is added to the balance of the card oralternatively, may be non-reloadable or disposable, such that additionalfunds cannot be added to the balance of the card. Stored value prepaidcards are advantageous for consumers who are unable to obtain a creditcard or do not want a credit card but still want the convenience ofbeing able to purchase goods and services and access cash without theuse of checks.

Another type of prepaid card is an “open system prepaid card” such as apayroll prepaid card. Payroll prepaid cards are provided by employers tocompensate employees. The employee is issued a card that permits accessto an account established by the employer. Each pay period, theemployee's earned funds are automatically loaded onto the card andavailable on payday—similar to direct deposit. The payroll prepaid cardmay also be used to pay bonuses or other compensation to employees. Apayroll prepaid card is particularly useful for employees who do nothave a regular checking or savings account. Commercial entities may alsowant to use an open system prepaid card for non-employees as well, suchas to provide payments to vendors, pay insurance claims, provideemergency disaster relief, loyalty programs, annuities and customerrefunds. In addition, consumers may want to provide an open systemprepaid card for a third party. For example, parents may want to providetheir children with an open system prepaid card such that the parentsmay control the funds spent with the prepaid card.

Another type of prepaid card is a “closed system prepaid card” and iscommonly known as a “gift card”. A merchant offers customers a gift cardto be purchased for a fixed amount or provides a gift card to customersas an incentive. The gift card is then pre-funded with the specificdollar amount and can only be used at the merchant that provided thecard. The merchant may register the name of the cardholder when the giftcard is provided to the customer. Generally, gift cards are notreloadable.

Other types of prepaid cards are also available, such as GovernmentPrepaid Cards, Travel prepaid cards, etc. Each type of prepaid card ispre-funded with a specific dollar amount and may be either reloadable ornon-reloadable.

To provide prepaid cards to a customer, an issuer first establishes aprepaid card program with a prepaid card processing system. The issuercommunicates certain default prepaid card program options and servicesto a prepaid card processing system for processing and storage. Then,any prepaid card issued by the issuer under the prepaid card program isconfigured with the default options by the prepaid card processingsystem. These default options may not be customized for a specificcustomer or order. Since the customer or issuer has no flexibility inoverriding the default options determined at the prepaid card programlevel, these default options may not be customized for a specificcustomer or order. However, with so many different types of customersand uses for a prepaid card, more flexibility may be desired by theissuer and/or customer, especially with respect to the expirationoptions for a prepaid card. Therefore, a need exists for a more flexibleprepaid card processing system that is operable to process customizedexpiration options for prepaid cards.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of an embodiment of a systemoperable to process custom expiration parameters for prepaid cards inaccordance with the present invention;

FIG. 2 is a schematic block diagram of an embodiment of a database in aprepaid card platform in accordance with the present invention;

FIG. 3 is a schematic block diagram of an embodiment of a prepaid cardapplication device in accordance with the present invention;

FIG. 4 is a logic diagram of an embodiment of a method for processing ofprepaid card program data in accordance with the present invention;

FIG. 5 is a logic diagram of an embodiment of a method for processingcustom expiration parameters in accordance with the present invention;

FIG. 6 is a schematic block diagram of an embodiment of a graphical userinterface for receiving custom expiration parameters in accordance withthe present invention;

FIG. 7 is a logic diagram of an embodiment for a method for processing acustom expiration date for a prepaid card in accordance with the presentinvention;

FIG. 8 is a logic diagram of an embodiment for a method for processing acustom expiration date for a replacement prepaid card; and

FIG. 9 is a logic diagram of an embodiment for a method for processingcustom expiration dates during auto re-issuance for a prepaid card.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

FIG. 1 is a schematic block diagram of an embodiment of a systemoperable to process custom expiration parameters for prepaid cards inaccordance with the present invention. The system 10 includes a prepaidcard processing system 12, proprietary network 14, network gateway 16,network 18, an issuer system 20, customer systems 22, 24, 26 and cardmanufacturer system 28. In an embodiment, the prepaid card processingsystem 12 and the issuer system 20 are operated and maintained asseparate systems by different legal entities. In another embodiment, theprepaid card processing system 12 and the issuer system 20 are operatedand maintained as one card processing and issuance system owned by asingle legal entity or owned by a parent and/or its subsidiary legalentities.

In an embodiment, the prepaid card processing system 12 communicateswith the issuer system 20 through a network 18, network gateway 16 andproprietary network 14. The proprietary network 14 includes one or moreinterconnected networks, having one or more network nodes, such asrouters, switches, gateways, bridges, hubs, switches and other networknodes that are managed by one or more network management systems toprovide secure channels of communication using one or more networkprotocols. In an embodiment, the proprietary network 14 is VisaNet™ or asimilar proprietary network. The prepaid card processing system 12 andthe proprietary network 14 may be operated and maintained by a singleentity or owned by a parent and/or its subsidiary legal entities. Forexample, Visa, Inc. operates and maintains its VisaNet™ proprietarynetwork and a VISA™ prepaid card processing system. In anotherembodiment, the prepaid card processing system 12 and the proprietarynetwork 14 are owned and operated by different legal entities.

The network 18 provides access to the proprietary network 14 through thenetwork gateway 16. The network 18 may be a wide area network, such asthe internet, or an access network or another proprietary network thatconnects devices to the proprietary network 14 through the networkgateway 16. The network gateway 16 may be one or more edge network nodesthat control access to the proprietary network 14 and may also providefirewall and routing services to the proprietary network 14 to ensureonly authorized communications are transmitted in the proprietarynetwork 14.

The issuer system 20 communicates to one or more customer systems, suchas customer systems 22, 24, 26 through the network 18. The issuer system20 and each customer system 22, 24, 26 and manufacturer system 28include network interfaces 30, 32, 34, 36 and 38. The network interfaces30, 32, 34, 36 and 38 provide network access for the customers andmanufacturer systems. The network interfaces 30, 32, 34, 36 and 38 mayinclude gateways, proxy servers, modems, network terminals and otherdevices that are operable to provide communication between the issuersystem 20 and the customer system 22, 24, 26 through the network 18. Inanother embodiment, the network interfaces 30, 32, 34, 36 and 38 may beoperable to provide communications between the issuer system 20 and thecustomer systems 22, 24, 26 through the network gateway 16 and theproprietary network 14.

The prepaid card processing system 12 includes a prepaid card processingsystem (PPCPS) interface device 40 that interfaces with the proprietarynetwork 14 to communicate with the issuer system 20 and customer systems22, 24, 26 and manufacturer system 28. In an embodiment, the PPCPSinterface device 40 includes a server, such as a web or file server,that is operable to communicate using the Hyper Text Transfer Protocol(HTTP) protocol, File Transfer Protocol (FTP) or other protocol operableto communicate data, such as Hypertext Markup Language (HTML) documents,text, images, audio, videos or some other type of file. The PPCPSinterface device 40 in an embodiment may transmit dynamic contentgenerated by it or by the prepaid card application device 42. The PPCPSinterface device 40 in an embodiment also includes firewall orauthentication capability that requires password or other authenticationdata prior to allowing access to some or all of the resources of theprepaid card processing system 12. The PPCPS interface device may alsoinclude gateways, proxy servers, modems, network terminals and otherdevices that are operable to provide communication.

The prepaid card processing system 12 includes a prepaid cardapplication device that is operable to perform functions describedherein to process prepaid cards. The prepaid card processing system 12also includes a PPCPS database 44. The database 44 may be one or moredatabases implemented in internal memory devices, storage area networks,network attached storage devices, or other storage devices located inone geographical location or multiple geographical locations. Thedatabase 44 may be structured as relational, network, hierarchal orobject based or other type of structured database operable to store andlocate data files.

The issuer system 20 includes the network interface 30 and the issuerdevice 46. The issuer device 46 in an embodiment includes a web browserfor receiving and sending data to the PPCPS interface device 40. Inaddition, the issuer device 46 or network interface 30 may include a webserver as well for communicating data with customers 22, 24 and 26 overnetwork 18. The issuer device 46 also includes a memory, either internalor external, and processing module that are operable to performfunctions described herein to issue prepaid cards.

To establish a prepaid card program, the issuer system 20 communicatesinformation about a prepaid card program to the prepaid card processingsystem 12. A prepaid card issued in accordance with the program includesa stored value prepaid card, an open system prepaid card, a closedsystem prepaid card, either reloadable or disposable, such as travelcard, payroll card, teen or student prefunded card, commercial prepaidcard, gift card, electronic payment account and any other type ofpreloaded or prefunded card or account, in any type of physical orelectronic form, including a plastic card, smart card, microchip,wireless device, electronic fund account, etc. An issuer is a bank,financial institution or other entity that issues a prepaid card tocommercial entities or consumers.

The information about the prepaid card program also includes programexpiration parameters. Upon receipt, the prepaid card processing system12 creates an issuer card program file for the issuer prepaid cardprogram with the program expiration parameters and stores the issuercard program file in the database 44. The program expiration parametersdefine default expiration parameters for determining expiration dates ofprepaid cards issued under the prepaid card program. In addition, theprogram expiration parameters indicate whether one or more customizedexpiration parameters are accepted under the issuer prepaid cardprogram. The issuer card program file may also include other data neededfor establishing the issuer prepaid card program with the prepaid cardprocessing system 12.

Once the prepaid card program is established, an issuer is operable toissue prepaid cards to its customers for use by cardholders. Acardholder includes but is not limited to an individual consumer orcommercial entity issued a prepaid card or batch of prepaid cards orauthorized to use a prepaid card. The issuer system 20 may communicateand issue cards to various types of customers. For example, one type ofcustomer is a commercial customer 22. The commercial customer system 22includes network interface 32 and customer device 48. The customerdevice 48 in an embodiment includes a web browser for receiving andsending data to the issuer system 20 or to the prepaid card processingsystem 12. The customer device 48 also includes a memory, eitherinternal or external, and processing module that are operable to performfunctions described herein.

In an embodiment, the commercial customer system 22 receives input froma user for a prepaid card order for a prepaid card or a plurality ofprepaid cards. In an embodiment, the prepaid card order may be receivedusing a web browser running on the customer device 48 that accesses aprepaid card order graphical user interface (GUI) program, such as HTMLdocuments, downloaded from a web server at either the issuer system 20or prepaid card processing system 12. In another embodiment, the prepaidcard order data may be received using another type of program, such as aspreadsheet or other specialized program, and processed by thecommercial customer system 22 to create a data file. The data file wouldhave a known format to the prepaid card processing system 12 for prepaidcard order data.

The prepaid card order may include an order for one or more prepaidcards. It may include other data, such as to identify the issuer,customer, prepaid card program, shipping address for the prepaid cards,etc. The prepaid card order may include cardholder data or thecardholder data may be provided at a later time. The prepaid card ordermay also include one or more customized expiration parameters.

In an embodiment, the commercial customer system 22 transmits theprepaid card order to the issuer system 20. The issuer system 20receives the prepaid card order and then transmits some or all of thedata from the prepaid card order to the prepaid card processing system12. In another embodiment, the commercial customer system 22 may accessthe prepaid card processing system 12 and transmit the prepaid cardorder to the prepaid card processing system 12 without firsttransmitting it to the issuer system 20.

When the prepaid card processing system 12 receives the prepaid cardorder, it creates and stores a card order file in the database 44. Theprepaid card processing system 12 also determines an expiration dateaccording to the one or more customized expiration parameters whenaccepted by the program expiration parameters. When determining theexpiration date, the one or more customized expiration parameters, thatare accepted, override the default expiration parameters from theprepaid card program file. The expiration date will apply to any prepaidcards that are part of the prepaid card order. The prepaid cardprocessing system 12 creates a set of card accounts for the prepaid cardorder in the database 44. For example, if the prepaid card orderincludes a request for one prepaid card, the set of card accountscreated includes one card account. If the prepaid card order includes arequest for a plurality of cards, the set of card accounts includes aplurality of card accounts such that one card account is created foreach prepaid card in the plurality of prepaid cards. The same expirationdate for each prepaid card in the prepaid card order is stored in eachcard account file.

The card account file for each prepaid card is transmitted by theprepaid card processing system 12 to the issuer system 20 for processingand acceptance. When accepted, the issuer system issues the prepaid cardand may also establish a card bank account for each card account file,if not already created. In an embodiment, when acceptance is received bythe prepaid card processing system 12, card manufacturing informationfor card accounts with a physical prepaid card is transmitted by theprepaid card processing system 12 to a card manufacturer system 28. Thecard manufacturer system 28 includes a network interface 38 andmanufacturer device 28. The manufacturer device 28 includes a memory,either internal or external, and processing module 50 that are operableto process the card manufacturing information to fabricate each prepaidcard in accordance thereof. The prepaid card or cards from the prepaidcard order is shipped to the shipping address indicated in the prepaidcard order.

In an embodiment, if the card order includes a shipment address to thecommercial customer 22 and did not include cardholder data, then theprepaid cards in the order are considered “instant issue” type prepaidcards. The instant issue prepaid cards are issued to a commercialcustomer 22. The commercial customer 22 must transmit cardholder data tobe associated with each prepaid card account to register or enroll thecardholders with the card processing module 12. When the cardholder datais received by the card processing module 12, the card processing module12 will store the cardholder data in the card account file associatedwith the prepaid card and activate the prepaid card. The commercialcustomer 22 prefunds the card bank accounts established by the issuersystem 20. The commercial customer 22 distributes the prepaid cards toeach respective cardholder, such as cardholders 52, 54, for use. Inanother embodiment, cardholder data and shipping address for thecardholder is provided in the prepaid card order. Such prepaid cards areconsidered “mail order or .CSV” type prepaid cards and must be activatedby the cardholder prior to use.

In an embodiment, the commercial customer 22 is an employer and theprepaid card order is for payroll cards for employees. Each employeereceives a prepaid payroll card. Each pay period, the employee's earnedfunds are automatically deposited into the card bank accounts in theissuer system 20 on payday—similar to direct deposit.

In another embodiment, the commercial customer is a merchant customer 24with a merchant customer system. The merchant customer system 24includes a network interface and customer device 56. The customer device56 is similar to the customer device 48 such that it is operable toreceive input from a user for a prepaid card order for one or moreprepaid cards. The prepaid card order also includes customizedexpiration parameters that are transmitted to the prepaid cardprocessing system 12. In this embodiment, the prepaid cards may be giftcards to be purchased or provided by the merchant customer 24 at one ormore retail stores 58. In this embodiment, instant issue type gift cardsmay be ordered and shipped to the merchant stores 58. When a customerpurchases the gift card, cardholder data for the cardholder 62 to beassociated with a prepaid card is collected and transmitted by a POSterminal 60 in the merchant stores to the merchant customer system 24.The merchant customer system 24 transmits the cardholder data to beassociated with a prepaid card to the prepaid card processing system 12.When received by the prepaid card processing system 12, the card accountfile is updated and the gift card may be activated, either by thecardholder or by the POS terminal 60.

In another embodiment, a customer is an individual consumer customer 26having a consumer customer system 26. The consumer customer system 26includes a network interface and customer device 56. The customer device56 is similar to the customer device 48 and 56 such that it is operableto receive input from a user for a prepaid card order for one or moreprepaid cards. In an embodiment, the customer device in general includesa web browser that accesses through the network interface 36 a webserver of the issuer system 20. The customer system 26 transmits aprepaid card order that also includes customized expiration parametersthat are transmitted to the prepaid card processing system 12.

FIG. 2 is a schematic block diagram of an embodiment of the database 44in accordance with the present invention. FIG. 2 illustrates the type ofinformation that may be stored by the prepaid card processing system 12in database 44 in an embodiment of the invention. When an issuer cardprogram is established, the prepaid card processing system 12 storesinformation about the issuer card program in the database 44. Thisinformation is illustrated by the issuer card program file 100. Theissuer card program file 100 includes a program identification 82 and anissuer identification 84.

In addition, the issuer card program file 100 includes programexpiration parameters 106 for the issuer prepaid card program file 100.The program expiration parameters 106 include default expirationparameters 108. The default expiration parameters 108 are used todetermine the default expiration date of a prepaid card issued under theissuer card program. The default expiration parameters 108 only includea standard card life cycle 110 that defines a time period, such as 6months, 12 months or 18 months, from the issue or activation date of aprepaid card to the expiration date of the prepaid card. The defaultexpiration parameters 108 may include more than one standard life cycle110. For example, the standard life cycles 110 in the default expirationparameters 108 may be 6 months, 12 months or 18 months. In knownsystems, an issuer or customer may only select expiration options fromthe default expiration parameters 108. The default expiration parameters108 provide little flexibility to an issuer or customer to change theexpiration date for a prepaid card order since the expiration date forthe prepaid card order may only be determined by a standard life cycle110 defined by the default expiration parameters 108. In addition, thedefault expiration parameters 108 provide no flexibility in definingcustom expiration dates for replacement prepaid cards or reissue prepaidcards.

In an embodiment, the program expiration parameters 106 in the issuercard program file 100 also include custom acceptance parameters 112. Thecustom acceptance parameters 112 indicate whether one or more customizedexpiration parameters are accepted for a prepaid card issued under theissuer prepaid card program. The custom acceptance parameters 112include a program custom expiration parameter 114, card replacementexpiration parameter 116, grace period expiration parameter 118 and autore-issuance expiration parameter 120. The program custom expirationparameter 114 indicates whether a customized expiration date is acceptedfor a prepaid card. The card replacement expiration parameter 116indicates whether recalculation of an expiration date for a replacementprepaid card is accepted. The grace period expiration parameter 118indicates whether a custom grace period for a replacement prepaid cardis accepted when a replacement card is requested within a predeterminedtime period of its expiration date. The auto re-issuance expirationparameter 120 indicates whether a custom auto-reissuance period isaccepted for determining expiration dates of prepaid cards that arere-issued under the issuer prepaid card program. Other custom acceptanceparameters 112 may also be included in an issuer prepaid card program.

In an embodiment, the program expiration parameters 106 may also includeexpiration criteria 86. The expiration criteria 86 include predeterminedcriteria for the custom expiration parameters. For example theexpiration criteria 86 may include a maximum card life cycle or otherlimits to the customized expiration parameters.

When the prepaid card processing system 12 receives a prepaid card orderunder the issuer prepaid card program file 100, it stores informationabout the prepaid card order in the database 44. This information isillustrated by the prepaid card order file 102 in FIG. 2. The prepaidcard order file 102 may include data for program identification 82,program identification 84, order identification 122 and customeridentification 124. The prepaid card order file 102 may also include ashipping address 126 for shipment of each prepaid card in the prepaidcard order. The prepaid card order file 102 also includes a quantity 128of prepaid cards desired by the customer under the prepaid card order.The quantity 128 may be one or more than one prepaid card. The prepaidcard order file 102 may also include cardholder data 130 for eachprepaid card. If the cardholder data 130 is not included in the prepaidcard order, it may be provided to the prepaid card processing system 12prior to activation of a prepaid card. The prepaid card order file 102also includes one or more customized expiration parameters 132 receivedby the prepaid card processing system 12 for the prepaid card orderunder the issuer prepaid card program. When accepted, the one or morecustomized expiration parameters 132 are used by the prepaid cardprocessing system 12 to determine an expiration date for any prepaidcard in the prepaid card order. The one or more customized expirationparameters 132 override any applicable default expiration parameters 108to determine the expiration date for any prepaid card in the prepaidcard order.

The customized expiration parameters 132 include a customized expirationdate 134, a customized recalculation parameter 136, a grace period 138and an auto re-issuance period 140. The customized expiration date 134may be a customized fixed expiration date 142 or a customized card lifecycle 144. A fixed expiration date 142 is a specific date of the monthand year or it can be just a month and a year. For example, the fixedexpiration date 142 may be Jan. 31, 2010 or it can be January 2010. Thecustomized card life cycle is a time period defined by any measurementunit of time. For example, the time period may be specified in a numberof days or months or hours, such as 60 days or 2 months or 1440 hours.The customized recalculation parameter 136 indicates whether anexpiration date should be recalculated for a replacement prepaid card.It may also include a replacement customized card life cycle 156 andreplacement customized card life cycle 154. The grace period 138 is atime period defined by any measurement unit of time that is used toextend an expiration date for a replacement prepaid card. The autore-issuance period 140 is a fixed expiration date or a customized cardlife cycle that determines an expiration date for an auto re-issuedprepaid card.

The prepaid card processing system 12 creates a set of card accounts forthe prepaid cards requested in the prepaid card order in the database44. The prepaid card processing system 12 stores information about acard account in the database 44. This information is illustrated by thecard account file 104 in FIG. 2. The card account file 104 may includedata for program identification 82, program identification 84, orderidentification 122, customer identification 124 and accountidentification 146. The card account file 104 includes an expirationdate 148 determined by the prepaid card processing system. In addition,the type of card 150 may be included in the card account file. Forexample, the type of card 150 may indicate if it is a first issued,re-issued or replacement card. In an embodiment, a card value 152 mayalso be included to track the balance of the funds on the prepaid card.In another embodiment, the card value 152 may be tracked by the issuersystem 20 in addition to or alternatively to the prepaid card processingsystem 12. In an embodiment, the card account file 104 may also includethe customized expiration parameters 132 applicable to the card accountfrom the prepaid card order.

Though FIG. 2 illustrates an issuer card program file 100, card orderfile 102 and card account file 104, the database 44 may store the dataillustrated using other file formats or using other database structures.

FIG. 3 is a schematic block diagram of an embodiment of the prepaid cardapplication device 42 in accordance with the present invention. Theprepaid card application device 42 includes an input/output (I/O) module160, a processing module 162 and a memory 164. In an embodiment, theprepaid card application device 42 includes one or more servers,computers or similar processing devices. In such an embodiment, theprocessing module 162 includes a central processing unit; the memory 164includes system memory, cache memory, and read only memory; the I/Omodule 160 includes a graphical user interface and/or a peripheraldevice interface (e.g., to connect to a mouse, a keyboard, etc.) and avideo card, printer card, etc. In general, the processing module 162 maybe a single processing device or a plurality of processing devices. Sucha processing device may be a microprocessor, micro-controller, digitalsignal processor, microcomputer, central processing unit, fieldprogrammable gate array, programmable logic device, state machine, logiccircuitry, analog circuitry, digital circuitry, and/or any device thatmanipulates signals (analog and/or digital) based on hard coding of thecircuitry and/or operational instructions. The processing module 162 mayhave internal memory and/or is coupled to memory 164. Memory 164 andinternal memory may each be a single memory device or a plurality ofmemory devices. Such a memory device may be a read-only memory, randomaccess memory, volatile memory, non-volatile memory, static memory,dynamic memory, flash memory, cache memory, and/or any device thatstores digital information. Note that when the processing moduleimplements one or more of its functions via a state machine, analogcircuitry, digital circuitry, and/or logic circuitry, the memory storingthe corresponding operational instructions may be embedded within, orexternal to, the circuitry comprising the state machine, analogcircuitry, digital circuitry, and/or logic circuitry. Further note that,the internal memory and/or memory 164 stores, and the processing module162 executes, hard coded and/or operational instructions correspondingto at least some of the steps and/or functions illustrated in FIGS. 1-9.

FIG. 4 is a logic diagram of an embodiment of a method for processing ofprepaid card program data in accordance with the present invention. Themethod begins at step 180 with receiving data about the prepaid cardprogram. In general, the prepaid card program data is input at orreceived by the issuer system 20. The issuer system 20 transmits theprepaid card program data to the prepaid card processing system 12. Whenthe prepaid card processing system 12 receives the prepaid card programdata, it creates an issuer card program file 100 for the issuer prepaidcard program as shown in step 182 of FIG. 4. The issuer card programfile 100 is stored in the database 44. As seen in FIG. 2, the issuercard program file 100 includes the program expiration parameters. Theissuer card program file 100 may also include other data needed forestablishing the issuer prepaid card program with the prepaid cardprocessing system 12.

FIG. 5 is a logic diagram of an embodiment of a method for processingthe customized expiration parameters 132 in accordance with the presentinvention. In step 202, card order data such as the data in card orderfile 102 is received by the prepaid card processing system 12. The cardorder may be for one or more first issued prepaid cards, replacementcards or re-issued prepaid cards. In an embodiment, the PPCPS interfacedevice 40 is a web server, and the issuer system 20 or a customer system22, 24, 26 accesses a web page from the PPCPS interface device 40 todownload a card order graphical user interface (GUI) in an HTMLdocument. The issuer system 20 or a customer system 22, 24, 26 receivescard order data inputs to the HTML document and transmits the card orderdata to the PPCPS interface device 40. In another embodiment, the cardorder data is received in a data file with a predetermined formatrecognized by the prepaid card processing system 12. The prepaid cardprocessing system 12 receives the card order data which includes one ormore customized expiration parameters 132 and stores the card order datain database 44, such as in the card order file 102. In step 204, theprepaid card application device 42 determines whether the programexpiration parameters 106 indicate acceptance of the one or morecustomized expiration parameters 132.

In an embodiment, customized expiration parameters may only be receivedas part of a prepaid card order by the customer systems 22, 24, and 26when the program expiration parameters indicate their acceptance. Forexample, the prepaid card order GUI downloaded from the prepaid cardprocessing system 12 may only include options to receive and selectcustomized expiration parameters when the program expiration parametersindicate their acceptance under the issuer prepaid card program for thecustomer. In another embodiment, the prepaid card order GUI may includeoptions to select customized expiration parameters for each orderregardless of whether the program expiration parameters indicate theiracceptance. However, though the prepaid card processing system 12 mayreceive the customized expiration parameters, the customized expirationparameters are only processed by the prepaid card processing system 12for the card order when the program expiration parameters indicate theiracceptance. Similarly, in another embodiment, the customer systems 22,24, 26 may receive and process a data file with prepaid card order dataincluding customized expiration parameters. But again, though theprepaid card processing system 12 may receive the data file withcustomized expiration parameters 132, the customized expirationparameters 132 are only processed by the prepaid card processing system12 for the prepaid card order when the program expiration parameters 106indicate their acceptance.

When accepted, the prepaid card processing system 12 processes thecustomized expiration parameters in step 206 and determines whether thecustomized expiration parameters meet predetermined criteria in step208. The predetermined criteria include the expiration criteria 86 andother system criteria. For example, the expiration criteria 86 may limitexpiration dates to two years from the issuance date. If the customizedexpiration parameters 132 include a fixed expiration date 142 that ismore than two years from the date of the card order, then the customizedexpiration parameters 132 would not meet the expiration criteria. Inanother example the expiration criteria 86 may provide for a minimumperiod to a fixed expiration, especially for mail order type prepaidcards. For example, the expiration criteria 86 may provide for a minimumof 10 days from a card order to a fixed expiration date for a mail ordertype prepaid card because processing, manufacture and shipment of a mailorder type prepaid card may average 10 days. Thus, a fixed expirationdate of 5 days for a mail order type card would not meet the expirationcriteria 86.

When the customized expiration parameters fail to meet the predeterminedcriteria, then a warning message may be transmitted by the prepaid cardprocessing system 12 that requests one or more revised customizedexpiration parameters 132. When the customized expiration parameters 132fail to meet the predetermined criteria or no customized expirationparameters 132 are received in the card order data, the prepaid cardapplication device 42 determines an expiration date of each prepaid cardin the card order based on the default expiration parameters 108 underthe issuer card program, as shown in step 210. When one or more of thecustomized expiration parameters 132 meet the predetermined criteria,the prepaid card application device 42 determines an expiration date ofeach prepaid card in the card order according to the one or morecustomized expiration parameters 132 as shown in step 212. The one ormore customized expiration parameters 132 may indicate the expirationdate for a prepaid card, a re-issue expiration date for reissuance of aprepaid card, a grace expiration period for a prepaid card, an autore-issuance expiration period for a prepaid card, or a replacementexpiration date for replacement of the prepaid card. Thus, theexpiration date may apply to a prepaid card, a replacement prepaid cardor an auto re-issued prepaid card.

The card processing module 12 creates or updates a card account file 104in the database 44 for each prepaid card in the card order with theexpiration date 148 determined by the prepaid card application device42, as shown in step 214. For a replacement or auto-reissued prepaidcard, a card account file 104 associated with the replacement orauto-reissued prepaid card may already exist. When a card account file104 already exists, the card account file is updated with the newexpiration date determined by the prepaid card application device 42,and the card type 150 may also be updated to indicate a replacement orreissued card type.

The prepaid card application device 42 determines in step 216 whetherthe card order is for an instant issue type prepaid card or a mail ordertype prepaid card. For an instant issue type prepaid card, the cardorder includes a shipment address to a commercial customer 22, 26 andthe prepaid cards are issued to a commercial customer. For a mail ordertype prepaid card, cardholder data and shipping address for thecardholder is provided to the prepaid card processing system 12. Whenthe prepaid card is not an instant issue card, the prepaid cardprocessing system 12 provides data from the card account file 104 to anissuer system 20 to issue a prepaid card for the card account file 104as shown in step 218. When processed and accepted, the issuer system 20issues the prepaid card to a cardholder and may also establish a cardbank account for each card account file 104, if not already created. Inan embodiment, when acceptance is received by the prepaid cardprocessing system 12, card manufacturing information for each cardaccount file 104 is transmitted by the prepaid card processing system 12to the card manufacturer system 28. The prepaid card is shipped to thecardholder by the card manufacturer system 28. When the prepaid card isreceived by the cardholder, the cardholder must activate the prepaidcard by transmitting activation data to the prepaid card processingsystem 12. When the activation data is received by the prepaid cardprocessing system 12 as shown in step 220, the prepaid card processingsystem 12 activates the prepaid card as shown in step 222.

When the prepaid card is an instant issue card, the prepaid cardprocessing system 12 provides data from the card account file 104 to anissuer system 20 to issue a prepaid card for the card account file 104as shown in step 224. When processed and accepted, the issuer system 20issues the prepaid card to a commercial or merchant customer, such ascustomers 22 and 24. The issuer system 20 may also establish a card bankaccount for each card account file 104, if not already created. Thecustomer 24, 26 or issuer system 20 transmits cardholder data for theissued prepaid card to the prepaid card processing system 12. When thecardholder data for the prepaid card is received by the prepaid cardprocessing system 12 as shown in step 224, the prepaid card processingsystem 12 must determine whether the expiration date 148 for the prepaidcard is greater than a predetermined time period as shown in step 228.When the expiration date 148 is less than a predetermined time period,then the card processing system may reject the activation as shown instep 230. For example, it may be determined that at least 2 days arerequired prior to expiration of a card for activation. Thus, apredetermined time period of 2 days may be set. When the cardholder datafor a prepaid card is received on a date wherein the expiration date isless than 2 days away, the prepaid card processing module 12 may rejectactivation of the prepaid card as shown in step 230. When the expirationdate 148 is greater than the predetermined time period, the cardprocessing system updates the card account file 104 with the cardholderdata as shown in step 232 and activates the prepaid card as shown instep 222.

FIG. 6 is a schematic block diagram of an embodiment of a card ordergraphical user interface (GUI) 260 for receiving custom expirationparameters in accordance with the present invention. In an embodiment,the card order GUI 260 is displayed using a web browser running on acustomer device 48 or issuer device 46 that accesses a prepaid cardorder graphical user interface (GUI) program, such as HTML documents,downloaded from a web server at either the issuer system 20 or prepaidcard processing system 12. The card order GUI 260 includes a toolbar 262for selecting one or more different tasks 268 and reports 270. Othercategories and options may also be provided by the toolbar 262. Thedifferent tasks 268 include new order 272. The new order task 272 isselected on the toolbar 262 such that the new card order GUI 264 isdisplayed. The card order GUI 260 includes fields for card order dataincluding issuer identification 84, card program identification 82,customer identification 124, shipping information 126, quantity 128,cardholder data 130, card type 150 and card value 152. The card orderGUI 260 also includes a field for default expiration date 282. Thedefault expiration date 282 is determined from the default expirationparameters 108. Instead of or in addition to the default expiration date282, the default expiration parameters 108 may be displayed as part ofthe card order GUI.

In an embodiment, the card order GUI 260 also includes fields forinputting one or more of the customized parameters 132. A field for thecustomized expiration date 134 provides for selection of a customizedexpiration date. When selected, a customized card life cycle 144 orcustomized fixed expiration date 142 may be selected as the customizedexpiration date 134. If not selected, default expiration date 282 willbe determined based on the default expiration parameters 108. A fieldfor the customized recalculation parameter 136 provides for selection ofwhether an expiration date should be recalculated for a replacementprepaid card. It may also include a replacement customized card lifecycle 156 and replacement customized card life cycle 154. A field forcustomized grace period 284 provides for selection of a customized graceperiod. When selected, a grace period 138 may be selected. The graceperiod 138 is used to extend an expiration date for a replacementprepaid card when requested within a predetermined time period from theexpiration date. A field for selection of a customized auto re-issuanceperiod 286 provides for selection of an auto re-issuance period. Whenselected, an auto re-issuance period 140 may be selected. The autore-issuance period 140 provides for a fixed expiration date or acustomized card life cycle that determines an expiration date for anauto re-issued prepaid card.

In operation, the issuer device 46 or the customer device 48, 56, 64 areoperable to display the card order GUI 260 and receive a selection ofone or more of the customized expiration parameters 132 from the issueror customer as part of the card order data. The selected one or morecustomized expiration parameters 132 are transmitted to the prepaid cardprocessing system 12. Though FIG. 6 illustrates a card order GUI 260 forreceiving one or more customized expiration parameters 132, othermethods and systems may be used to receive the one or more customizedexpiration parameters. In another embodiment, the prepaid card orderdata is received using another type of program, such as a spreadsheet orother specialized program, and processed to create a data file. The datafile is then transmitted to the prepaid card processing system 12. Inanother embodiment, a call center may collect card order data from acustomer or issuer using voice communication or text communication andprovide the prepaid card order data to the prepaid card processingsystem 12.

FIG. 7 is a logic diagram of an embodiment for a method for processing acustom expiration date 134 to determine an expiration date for a prepaidcard in accordance with the present invention. In step 302, defaultexpiration date 282 or default expiration parameters 108 are determinedby the prepaid card processing system 12 and transmitted to the customer24, 26 or issuer 20. The default expiration parameters 108 only includeone or more standard card life cycles 110, such as 6 months, 12 monthsor 18 months. The default expiration date 282 is determined based on thestandard card life cycle 110 by adding the standard card life cycle 110to the prepaid card order date, an issuance date or activation date todetermine the expiration date. By viewing the default expirationparameters 108, the customer 24, 26 or issuer 20 may determine whether acustomized expiration date 134 is preferred over the default expirationparameters 108.

In step 304, the prepaid card processing system 12 determines whetherthe program expiration parameters 106 indicate acceptance of acustomized expiration date 134. The prepaid card processing system 12accesses the issuer card program file 100 from the database 44 anddetermines whether the program custom expiration parameter 114 indicatesacceptance of a customized expiration date 134. When not accepted, theprepaid card processing system 12 determines an expiration date 148 fora prepaid card account file 104 based on the default expirationparameters 108 as shown in step 322. When accepted, an interface, suchas card order GUI 260 is provided to receive a customized expirationdate 134. When no customized expiration date 134 is received, then theprepaid card processing system 12 determines an expiration date 148based on the default expiration parameters 108 as shown in step 322.When a customized expiration date 134 is received, the prepaid cardprocessing system 12 determines an expiration date 148 for the cardaccount file 104 based on the customized expiration date 134 as shown instep 310. The customized expiration date 134 may be a customized cardlife cycle 144 or customized fixed expiration date 142. The customizedcard life cycle 144 may be selected for any time period and not just atime period provided in the standard card life cycle 110. The timeperiod is then added to the card order date, issuance date or activationdate to determine the expiration date 148. The customized fixedexpiration date 142 is a specific day of a month and year or it may bejust a month and a year. For example, the customized fixed expirationdate 142 may be Jan. 31, 2010 or it may be January 2010.

In step 312, the prepaid card processing system 12 processes theexpiration date 148 for the card account file 104 and determines whetherthe expiration date 148 meets predetermined criteria. The predeterminedcriteria include the expiration criteria 86 in the issuer card programfile 100 or other system criteria. For example, the expiration criteria86 may limit expiration dates to two years from the issuance date. Ifthe expiration date 148 is more than two years from the date of the cardorder, then the expiration date 148 does not meet the expirationcriteria. In another example the expiration criteria 86 may provide fora minimum period to the expiration date 148, especially for mail ordertype prepaid cards. For example, the expiration criteria 86 may providefor a minimum of 10 days from a card order to the expiration date 148for a mail order type prepaid card because processing, manufacture andshipment of a mail order type prepaid card may average 10 days. Thus, anexpiration date 148 of 5 days for a mail order type card would not meetthe expiration criteria 86. The predetermined criteria may only beadvisory. For example, the predetermined criteria may provide that anexpiration date 148 that is 30 days from a card order may be allowed buta warning message is generated to advise the issuer 20 or customer 22,24, 26 of the short expiration period.

When the expiration date 148 fails to meet the predetermined criteria,then a warning message is transmitted by the prepaid card processingsystem 12 that requests one or more revised customized expiration date134 as shown in step 314. When the expiration date 148 fails to meetadvisory criteria, the warning message may provide that an override ofthe warning is accepted. In step 316, when the customized expirationparameters 132 fail to meet the predetermined criteria and an overrideof the warning is not accepted or received, the prepaid card processingsystem 12 determines an expiration date 148 for the card account file104 based on the default expiration parameters 108, as shown in step322. When the expiration date 148 meets the predetermined criteria, theprepaid card processing system 12 provides acceptance of the card orderand stores the expiration date 148 based on the custom expiration date134 in the card account file 104, as shown in step 318. The prepaid cardprocessing system 12 then provides data from the card account file 104to an issuer system 20 to issue a prepaid card for the card account file104 as shown in step 320.

FIG. 8 is a logic diagram of an embodiment for a method for processing acustom expiration date for a replacement prepaid card. When a prepaidcard is lost or stolen or damaged, a request for a replacement card isreceived by the prepaid card processing system 12 in a prepaid cardorder as shown in step 342. The prepaid card order would include a cardtype 150 of “replacement” or “re-issue” and provide data to identify thecard account file 104. When the prepaid card processing system 12receives the request, it accesses the card account file 104 in thedatabase 44 to retrieve the expiration date 148 for the prepaid card.The prepaid card processing system 12 provides the expiration date 148in the card account file 104 to the customer 24, 26 or issuer 20. Theprepaid card processing system 12 then determines whether the expirationdate 148 is within a predetermined time period in step 346.

When the expiration date 148 is within a predetermined time period, suchas 5 or 10 days, of the request for card replacement, then the requestfor card replacement is processed in a different manner. As shown instep 348, the prepaid card processing system 12 determines whether agrace period expiration parameter 118 in the issuer card program file100 indicates acceptance of a grace period 138. When the grace periodexpiration parameter 118 in the issuer card program file 100 indicatesthat a grace period 138 is not accepted, a warning message is providedby the prepaid card processing system 12, as shown in step 350. Thewarning message advises the issuer 20 or customer 22, 24, 26 requestinga replacement card, that the request for a replacement card is rejected.The order request for a card replacement is then rejected, as shown instep 352. The prepaid card processing system 12 determines thepredetermined time period for example based on a time to process therequest for a replacement card, manufacturer the replacement card andship the replacement card. If no grace period is accepted, and theexpiration date is less than the predetermined time period, then therequest is rejected because the replacement card may not be received oractivated by a cardholder before the expiration date 148.

When the grace period expiration parameter 118 in the issuer cardprogram file 100 indicates that a grace period 138 is accepted for thecard account file 104, the prepaid card processing system 12 receives agrace period 138. In an embodiment, the grace period 138 may have beenreceived prior to the card replacement request in a previous prepaidcard order and stored in the card order file 102 or card account file104 associated with the prepaid card. The prepaid card processing system12 may then retrieve the grace period 138 from the card order file 102or card account file 104. In another embodiment, the prepaid cardprocessing system 12 provides an interface, such a card order GUI toenter the grace period 138 for the card replacement. The prepaid cardprocessing system 12 then determines a new expiration date for thereplacement card based on the grace period 138. For example, the graceperiod 138 may be added to the expiration date 148 to determine the newexpiration date. The new expiration date is stored in the card accountfile 104 as the expiration date 148. The type of card 150 may also beupdated to indicate a replacement card. The prepaid card processingsystem 12 then provides data from the updated card account file 104 tothe issuer system 20 to issue a replacement prepaid card for the cardaccount file 104 as shown in step 372.

Referring to step 346 in FIG. 8, when the expiration date 148 is notless than a predetermined time period, then the processing of therequest for card replacement determines whether the card replacementexpiration parameter 116 in the issuer card program file 100 indicatesacceptance of recalculation of an expiration date for a replacementcard. When not accepted, then the new expiration date for thereplacement card is based on the current expiration date 148 in the cardaccount file 104, as shown in step 362. When accepted, the prepaid cardprocessing system 12 determines whether to recalculate the expirationdate from the customized recalculation of expiration parameter 136, asshown in step 364. In an embodiment, the customized recalculation ofexpiration parameter 136 may have been received prior to the cardreplacement request in a previous prepaid card order and stored in thecard order file 102 or card account file 104 associated with the prepaidcard. The prepaid card processing system 12 may then retrieve thecustomized recalculation of expiration parameter 136 from the card orderfile 102 or card account file 104. In another embodiment, the prepaidcard processing system 12 provides an interface, such a card order GUIto enter the customized recalculation of expiration parameter 136 forthe card replacement request. In both embodiments, the prepaid cardprocessing system 12 receives the customized recalculation of expirationparameter 136. When the customized recalculation of expiration parameter136 indicates no recalculation for a replacement card under the cardaccount 104, the prepaid card processing system 12 determines the newexpiration date for the replacement card based on the current expirationdate 148 in the card account file 104, as shown in step 362.

When the customized recalculation of expiration parameter 136 indicatesrecalculation for a replacement card under the card account 104, theprepaid card processing system 12 determines a new expiration date forthe replacement card, as shown in step 368. For a card account file 104with a customized fixed expiration date, the prepaid card processingsystem 12 may provide for an interface to the issuer 20 or customer 22,24 to select a new replacement customized fixed expiration date 154,such as shown in the card order GUI 260. Certain predetermined criteriamay be required for the new customized fixed expiration date. Forexample, the new customized fixed expiration date may not be more thanthe time period between the request for a replacement card and thecurrent expiration date. The prepaid card processing system 12 may alsoallow for the grace period 138 to be added to the time period, such as10 days, to compensate for processing, manufacturing and shipping time.For example, if the expiration date 148 in the card account file 104 forthe prepaid card was only 30 days from the request for a replacementcard, then the new expiration date may not be more than 30 days placethe grace period or 40 days from the request for a replacement card.

For a card account file 104 with an expiration date 148 based on acustomized card life cycle, the prepaid card processing system 12 mayprovide for an interface to the issuer 20 or customer 22, 24 to select anew replacement customized card life cycle as shown on card order GUI260 for the replacement card. In another embodiment, an expiration datefor the replacement card may be recalculated based on the currentcustomized card life cycle. Certain predetermined criteria may berequired for the new expiration date based on the customized card lifecycle. For example, the predetermined criteria may specify that theelapsed time of the original prepaid card and the new customized cardlife cycle may not be more than the maximum card life cycle for aprepaid card under the issuer card program. For example, when theexpiration criteria 86 defines a maximum life cycle for a prepaid cardat two years and the original prepaid card has been issued for thirteenmonths, the new customized card life cycle may not exceed eleven months.The prepaid card processing system 12 may also allow for the graceperiod 138 to be added to the time period, such as 10 days, tocompensate for processing, manufacturing and shipping time.

The new expiration date for the replacement card is stored in the cardaccount file 104 as the expiration date 148, as shown in step 370. Thetype of card 150 may also be updated to indicate a replacement card. Theprepaid card processing system 12 then provides data from the updatedcard account file 104 to the issuer system 20 to issue a replacementprepaid card for the card account file 104 as shown in step 372.

FIG. 9 is a logic diagram of an embodiment for a method for processingcustom expiration dates during auto re-issuance for a prepaid card. Aprepaid card at expiration may auto re-issue according to options andcriteria defined by the issuer system 20. In step 402, the prepaid cardprocessing system 12 receives a request from the issuer system 20 orcustomers 22, 24, 26 for auto re-issuance of a prepaid card. The requestincludes a card type 150 of “re-issue” and provides data to identify thecard account file 104. The prepaid card processing system 12 accessesthe issuer card program file 100 associated with the prepaid card anddetermines whether the auto re-issuance expiration parameter 120 in theissuer card program file 100 indicates acceptance of a customizedauto-reissuance period 140. When not accepted, the prepaid cardprocessing system 12 determines an expiration date 148 for the re-issuedprepaid card based on the standard card life cycle 110 or other defaultexpiration parameters 108 as shown in step 406.

When accepted, an interface, such as card order GUI 260 is provided toreceive a customized auto re-issuance period 140. In an embodiment, thecustomized auto re-issuance period may have been received prior to theprepaid card re-issue request in a previous prepaid card order andstored in the card order file 102 or card account file 104 associatedwith the prepaid card. The prepaid card processing system 12 may thenretrieve the customized auto re-issuance period from the card order file102 or card account file 104. In another embodiment, the prepaid cardprocessing system 12 provides an interface, such a card order GUI toenter the customized auto re-issuance period for the prepaid cardre-issue request. In both embodiments, the prepaid card processingsystem 12 determines whether a customized auto re-issuance period isreceived, as shown in step 408. When no customized auto re-issuanceperiod 140 is received, then the prepaid card processing system 12determines an expiration date 148 for the re-issued prepaid card basedon the default expiration parameters 108 as shown in step 406.

When a customized auto re-issuance period 140 is received, the prepaidcard processing system 12 determines whether the expiration date 148 forthe prepaid card is based on a customized fixed expiration date, asshown in step 410. In an embodiment, the customized auto re-issuanceperiod 140 is only used only to determine a new expiration date tore-issue a prepaid card with a customized fixed expiration date 142.When a prepaid card with a customized fixed expiration date 142 isre-issued, the prepaid card processing system 12 determines the newexpiration date by adding the customized auto re-issuance period 140, asshown in step 412. For example, if the customized auto re-issuanceperiod 140 is 60 days then the new re-issued card will have anexpiration date determined by the customized fixed expiration date 148of the prepaid card plus 60 days. When a prepaid card with a customizedcard life cycle 144 is re-issued, the prepaid card processing system 12determines the new expiration date based on the customized card lifecycle 144, as shown in step 418. For example, if a prepaid card wasissued with a customized card life cycle of 6 months, then the re-issuedprepaid will have a new expiration date that is 6 months from the dateof the previous expiration date for the prepaid card.

In another embodiment of the invention, the customized auto re-issuanceperiod 140 may also be used to determine a new expiration date for aprepaid card with an expiration date based on the customized card lifecycle 144. In this embodiment, the prepaid card processing system 12determines the new expiration date for the re-issued card based on thecustomized auto re-issuance period. For example, if a prepaid card wasissued with a customized card life cycle of 6 months and the customizedauto re-issuance period is 7 months, then the re-issued prepaid willhave a new expiration date that is 7 months from the date of theprevious expiration date for the prepaid card.

The new expiration date for the re-issued prepaid card is stored in thecard account file 104 as the expiration date 148, as shown in step 414.The type of card 150 may also be updated to indicate a re-issued prepaidcard. The prepaid card processing prepaid card processing system 12 thenprovides data from the updated card account file 104 to the issuersystem 20 to issue a replacement prepaid card for the card account file104 as shown in step 416.

The embodiment of the present invention provides greater flexibility toan issuer 20 and customers 22, 24, 26 to configure the expiration datefor a prepaid card, the expiration date for a replacement of the prepaidcard and an expiration date for auto re-issuance of the prepaid card.Prepaid cards issued under an issuer card program are no longer subjectto only the default expiration parameters established by the issuer 20for the prepaid card program. The flexibility in determining expirationdates for a prepaid card, a replacement prepaid card and a re-issuedprepaid card is not only at a customer level, but the customizedexpiration parameters may differ between prepaid card orders from acustomer. This flexibility under a prepaid card program is advantageousfor new customers or new uses for a prepaid card or for orders withdifferent needs from a customer.

As may be used herein, the term “operable to” indicates that an itemincludes one or more of processing modules, data, input(s), output(s),etc., to perform one or more of the described or necessary correspondingfunctions and may further include inferred coupling to one or more otheritems to perform the described or necessary corresponding functions. Asmay still further be used herein, the term “associated with”, includesdirect and/or indirect association of separate data and/or one databeing embedded within another item.

The present invention has also been described above with the aid ofmethod steps illustrating the performance of specified functions andrelationships thereof. The boundaries and sequence of these functionalbuilding blocks and method steps have been arbitrarily defined hereinfor convenience of description. Alternate boundaries and sequences canbe defined so long as the specified functions and relationships areappropriately performed. Any such alternate boundaries or sequences arethus within the scope and spirit of the claimed invention.

The present invention has been described above with the aid offunctional building blocks illustrating the performance of certainsignificant functions. The boundaries of these functional buildingblocks have been arbitrarily defined for convenience of description.Alternate boundaries could be defined as long as the certain significantfunctions are appropriately performed. Similarly, flow diagram blocksmay also have been arbitrarily defined herein to illustrate certainsignificant functionality. To the extent used, the flow diagram blockboundaries and sequence could have been defined otherwise and stillperform the certain significant functionality. Such alternatedefinitions of both functional building blocks and flow diagram blocksand sequences are thus within the scope and spirit of the claimedinvention. One of average skill in the art will also recognize that thefunctional building blocks, and other illustrative blocks, modules andcomponents herein, can be implemented as illustrated or by one ormultiple discrete components, networks, systems, databases or processingmodules executing appropriate software and the like or any combinationthereof.

1. A method for processing expiration dates of prepaid cards,comprising: receiving program expiration parameters for an issuerprepaid card program; receiving one or more customized expirationparameters for a prepaid card in a prepaid card order under the issuerprepaid card program; determining an expiration date for the prepaidcard based on the one or more customized expiration parameters inaccordance with the program expiration parameters; and processing a cardaccount file for the prepaid card to store the expiration date for theprepaid card.
 2. The method of claim 1, further comprising: determiningthe expiration date for the prepaid card according to default expirationparameters when the program expiration parameters indicate that the oneor more customized expiration parameters are not accepted.
 3. The methodof claim 1, wherein the one or more customized expiration parametersinclude at least one of: a customized card life cycle and a customizedfixed expiration date.
 4. The method of claim 3, wherein determining theexpiration date for the prepaid card based on the one or more customizedexpiration parameters in accordance with the program expirationparameters, comprises: determining the expiration date for the prepaidcard is the customized fixed expiration date when the program expirationparameters indicate acceptance of a customized fixed expiration date. 5.The method of claim 3, wherein determining the expiration date for theprepaid card based on the one or more customized expiration parametersin accordance with the program expiration parameters, comprises:determining the expiration date for the prepaid card is equal to thecustomized card life cycle from an issue date of the prepaid card whenthe program expiration parameters indicate acceptance of a customizedcard life cycle.
 6. The method of claim 1, wherein determining theexpiration date for the prepaid card based on the one or more customizedexpiration parameters in accordance with the program expirationparameters, comprises: determining the expiration date for the prepaidcard based on the one or more customized expiration parameters when theprogram expiration parameters indicate acceptance of the one or morecustomized expiration parameters and the one or more customizedexpiration parameters meet predetermined criteria.
 7. The method ofclaim 1, further comprising: determining a second expiration date for areplacement of the prepaid card when indicated by a customizedrecalculation parameter and when the program expiration parametersindicate acceptance of the customized recalculation parameter.
 8. Themethod of claim 7 wherein determining the second expiration date for thereplacement of the prepaid card comprises: determining the secondexpiration date for the replacement of the prepaid card based on areplacement customized fixed expiration date when the expiration date ofthe prepaid card was based on a customized fixed expiration date; anddetermining the second expiration date for the replacement of theprepaid card based on a replacement customized card life cycle when theexpiration date of the prepaid card was based on a customized card lifecycle.
 9. The method of claim 1, further comprising: determining asecond expiration date for a replacement of the prepaid card based on agrace period when the program expiration parameters indicate acceptanceof the grace period.
 10. The method of claim 9, wherein determining thesecond expiration date for the replacement of the prepaid card based onthe grace period, comprises: adding the grace period to the expirationdate.
 11. The method of claim 1, further comprising: determining asecond expiration date for a re-issuance of the prepaid card based on anauto re-issuance period when the program expiration parameters indicateacceptance of the auto re-issuance period.
 12. The method of claim 11,wherein determining the second expiration date for the re-issuance ofthe prepaid card based on the auto re-issuance period, comprises: addingthe auto re-issuance period to the expiration date.
 13. A prepaid cardprocessing system, comprising: a database for storing: programexpiration parameters associated with an issuer prepaid card program; aset of card accounts created under the issuer prepaid card program,wherein a card account of the set of card accounts has an expirationdate for a prepaid card; and one or more customized expirationparameters for the prepaid card; a prepaid card application deviceoperable to: determine the expiration date for the prepaid cardassociated with the card account based on the program expirationparameters and the customized expiration parameters.
 14. The prepaidcard processing system of claim 13, wherein the program expirationparameters indicate whether the one or more customized expirationparameters are accepted for the set of card accounts created under theissuer prepaid card program.
 15. The prepaid card processing system ofclaim 14, wherein the one or more customized expiration parameterscomprise at least one of: a customized expiration date, wherein thecustomized expiration date defines an expiration date for the prepaidcard; a customized recalculation parameter, wherein the customizedrecalculation parameter indicates that the expiration date is to berecalculated for a replacement of the prepaid card; a grace period,wherein the grace period determines a second expiration date for areplacement of the prepaid card issued within a predetermined timeperiod before the expiration date of the prepaid card; and an autore-issuance period, wherein the auto re-issuance period determines are-issued expiration date for a re-issuance of the prepaid card.
 16. Theprepaid card processing system of claim 15, further comprising: aninterface device for communicating with an issuer system and a customersystem.
 17. The prepaid card processing system of claim 16, wherein theinterface device is operable to communicate a graphical user interfacefor receiving the program expiration parameters and the customizedexpiration parameters.
 18. A method for providing customized expirationdates of prepaid cards, comprising: transmitting program expirationparameters to establish a prepaid card program, wherein the programexpiration parameters include default expiration parameters and customacceptance parameters; and transmitting a prepaid card order with one ormore customized expiration parameters for a prepaid card for issuance inaccordance with the prepaid card program, wherein the customizedexpiration parameters provide an expiration date of the prepaid card.19. The method of claim 18, wherein the custom acceptance parameterscomprise two or more of: a program custom expiration parameter thatindicates whether a customized expiration date may be accepted for theprepaid card; a card replacement expiration parameter that indicateswhether customized expiration dates may be recalculated for areplacement of the prepaid card; a grace period expiration parameterthat indicates whether a grace period may be customized for areplacement of the prepaid card; and an auto re-issuance expirationparameter that indicates whether an expiration date may be customizedfor auto re-issuance of the prepaid card.
 20. The method of claim 18,wherein the customized expiration parameters comprise two or more of: acustomized expiration date, wherein the customized expiration datedefines an expiration date for the prepaid card; a customizedrecalculation parameter, wherein the customized recalculation parameterindicates that an expiration date should be recalculated for areplacement of the prepaid card; a grace period, wherein the graceperiod indicates a new expiration date for a replacement of the prepaidcard; and an auto re-issuance period, wherein the auto re-issuanceperiod defines a new expiration date for a re-issuance of the prepaidcard.
 21. The method of claim 20, further comprising: receiving awarning message in response to one or more of the customized expirationparameters not meeting predetermined criteria.
 22. A method for orderingprepaid cards with customized expiration parameters, comprising:accessing an interface of a prepaid card processing system; andtransmitting a prepaid card order under an issuer prepaid card programincluding customized expiration parameters, wherein the customizedexpiration parameters override default expiration parameters for theissuer prepaid card program to determine an expiration date of a prepaidcard requested in the prepaid card order.
 23. The method of claim 22,further comprising: receiving a prepaid card from the card order,wherein the expiration date of the card is determined from thecustomized expiration parameters; transmitting cardholder dataassociated with the prepaid card; when a number of days to theexpiration date of the prepaid card is greater than a predetermined timeperiod, receiving a confirmation of activation of the prepaid card; andwhen a number of days to the expiration date of the prepaid card is lessthan a predetermined time period, receiving a rejection of activation ofthe prepaid card.
 24. The method of claim 22, further comprising:receiving a warning message in response to one or more of the customizedexpiration parameters not meeting predetermined criteria; andtransmitting an override to the warning message.
 25. The method of claim22, wherein the customized expiration parameters comprise: a customizedexpiration date, wherein the customized expiration date defines anexpiration date for the prepaid card; a customized recalculationparameter, wherein the customized recalculation parameter indicates thatan expiration date should be recalculated for a replacement of theprepaid card; a grace period, wherein the grace period indicates a newexpiration date for a replacement of the prepaid card; and an autore-issuance period, wherein the auto re-issuance period defines a newexpiration date for a re-issuance of the prepaid card.